This test was failing for he wrong reason. Calls to block-attach after the
authordan@guaranine.beaverton.ibm.com <dan@guaranine.beaverton.ibm.com>
Sat, 12 Nov 2005 17:25:12 +0000 (18:25 +0100)
committerdan@guaranine.beaverton.ibm.com <dan@guaranine.beaverton.ibm.com>
Sat, 12 Nov 2005 17:25:12 +0000 (18:25 +0100)
commit47bb754959f271c5e61fce01930bec9ffce69024
tree00264ce0a6511c5eda4c35f22720c7359b2fabe0
parent8fc503a014a2d7da1435bf0096b393f2394c0f41
This test was failing for he wrong reason.  Calls to block-attach after the
first *should* report failure, so the test should not fail because of this.
The test now fails because multiple calls to block-attach seem to detach the
block devicem, which is wrong.

Signed-off-by: Dan Smith <danms@us.ibm.com>
tools/xm-test/tests/block-create/04_block_attach_device_repeatedly_pos.py